Flash management using separate metadata storage

ABSTRACT

Disclosed are techniques for flash memory management, including storing metadata and/or error correcting information separately from payload data. In various embodiments, metadata and/or error correcting information are stored in a random access memory within a solid state drive.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a non-provisional of U.S. Provisional No. 61/045,060 filed on Apr. 15, 2008 and entitled “FLASH MEMORY CONCEPTS.” This application is also a continuation-in-part of U.S. patent application Ser. No. 12/103,273 filed on Apr. 15, 2008, now U.S. Patent Application Publication No. 2009/0259800 entitled “FLASH MANAGEMENT USING SEQUENTIAL TECHNIQUES.” This application is also a continuation-in-part of U.S. patent application Ser. No. 12/103,277 filed on Apr. 15, 2008, now U.S. Patent Application Publication No. 2009/0259801 entitled “CIRCULAR WEAR LEVELING.” The entire contents of all of the foregoing applications are hereby incorporated by reference.

TECHNICAL FIELD

The present disclosure relates to information storage, particularly storage in flash memory systems and devices.

BACKGROUND

Flash memory is a storage medium which may be erased and written electronically. It is non-volatile, and therefore maintains the information contained within it without the need for power. It typically offers improved resistance to kinetic damage compared to other storage technologies, such as magnetic disks and tapes. However, the number of write and/or erase cycles which may be performed on any particular block of flash memory is finite. Because a flash memory device holds many individual memory blocks, write and/or erase cycles are often distributed across the entire memory array in order to extend the functional lifetime of each memory block.

Techniques for distributing write and/or erase cycles across a flash memory array are commonly known as wear leveling. Nevertheless, despite the existence of various such wear leveling techniques, it remains desirable to further improve the performance of flash memory in order to realize benefits such as improved read speeds, improved write speeds, and increased flash memory functional lifetime.

SUMMARY

This disclosure relates to flash memory management using separate metadata storage. In an exemplary embodiment, a method for flash memory management comprises storing at least one of metadata or error correcting information. The stored information is associated with one or more logical pages in a flash memory. A data table associated with the flash memory is constructed. Entries of the data table correspond to logical pages within the flash memory, and entries of the data table comprise at least one of metadata or error correcting information associated with the logical pages.

In another exemplary embodiment, a data storage system comprises a first memory configured for block-based erase operations, and a controller in communication with the first memory. The controller is configured to write incoming data to the first memory in the order the data is received. A second memory configured for random access is in communication with the controller. The second memory stores at least one of metadata or error correcting information, and the stored information is associated with one or more logical pages in a flash memory.

In yet another exemplary embodiment, a tangible computer-readable medium has instructions stored thereon. The instructions comprise instructions to store at least one of metadata or error correcting information. The stored information is associated with one or more logical pages in a flash memory. The instructions further comprise instructions to construct a data table associated with the flash memory. Entries of the data table correspond to logical pages within the flash memory, and entries of the data table comprise at least one of metadata or error correcting information associated with the logical pages.

The contents of this summary section are provided only as a simplified introduction to the disclosure, and are not intended to be used to interpret or limit the scope of the appended claims.

BRIEF DESCRIPTION OF THE DRAWINGS

With reference to the following description, appended claims, and accompanying drawings:

FIG. 1 represents a solid state drive and host computer system in accordance with an exemplary embodiment of the invention;

FIG. 2 discloses a flash controller in accordance with an exemplary embodiment of the invention;

FIG. 3A represents a flash chip containing erase blocks in accordance with an exemplary embodiment of the invention;

FIG. 3B represents an erase block containing pages in accordance with an exemplary embodiment of the invention;

FIG. 4 illustrates data structures in accordance with an exemplary embodiment of the invention;

FIG. 5A illustrates a solid state drive configured to store metadata associated with information contained in a flash chip array on a separately addressable flash chip in accordance with an exemplary embodiment of the invention; and

FIG. 5B illustrates a solid state drive having a metadata storage memory in accordance with an exemplary embodiment of the invention.

DETAILED DESCRIPTION

The following description is of various exemplary embodiments only, and is not intended to limit the scope, applicability or configuration of the present disclosure in any way. Rather, the following description is intended to provide a convenient illustration for implementing various embodiments including the best mode. As will become apparent, various changes may be made in the function and arrangement of the elements described in these embodiments without departing from the scope of the appended claims.

For the sake of brevity, conventional techniques for flash management may not be described in detail herein. Furthermore, the connecting lines shown in various figures contained herein are intended to represent exemplary functional relationships and/or physical couplings between various elements. It should be noted that many alternative or additional functional relationships or physical connections may be present in a practical flash memory management system.

For purposes of convenience, the following definitions may be used in this disclosure:

A page is a logical unit of flash memory.

An erase block is a logical unit of flash memory containing multiple pages.

Payload data is data stored and/or retrieved by a host, such as a host computer or other external data source.

Wear leveling is a process by which locations in flash memory are utilized such that the entire flash memory ages substantially uniformly, reducing localized overuse and associated failure of individual, isolated locations.

Metadata is data related to a portion of payload data (such as one page), which may provide identification information, support information, or other information to assist in managing payload data, such as to assist in determining the position of payload data within the storage context as understood by a host computer.

Prior flash memory management schemes often assume that pages within an erase block can be written in any order, and so allow payload data to be deposited non-sequentially. This simplifies the task of locating a specific block for retrieval by placing the blocks into a predefined order that allows addresses to be calculated using numerical methods instead of tabular methods, and has no bearing on the order in which blocks arrive from the host. These prior flash memory management schemes would sometimes additionally implement wear leveling techniques in order to increase the lifetime of a flash memory device. However, such flash memory management schemes often perform poorly when writing data that is substantially unsorted, fragmented, or otherwise disjoint (“random writes”). In these schemes, random write performance may be as much as two orders of magnitude slower than performance when writing substantially sorted, related, or contiguous data (“sequential writes”). In transaction-based computing systems and other high-load applications, data often comprises highly fragmented and/or random portions, rather than large, contiguous portions. As such, prior flash memory management schemes offer unsuitable performance for use in these areas, because the vast majority of write operations are random writes.

In contrast, in accordance with an exemplary aspect of the present invention, flash memory management is improved by writing payload data to a particular flash memory device in the order in which it was received, and/or in sequential order within an erase block. Thus, in essence, sequences of random data are written in the same manner as sequences of contiguous data. Such an approach can vastly improve random write performance, with minimal impact on sequential write performance. A flash memory device, such as a solid state drive, configured to achieve improved random write performance can better suit the needs of, for example, applications in the small block size enterprise storage market, such as database and database-like programs, and other applications which make frequent, small accesses to data storage. Moreover, sequential writing can improve flash memory management by reducing and/or eliminating various flash write issues, for example trapped charge relaxation errors due to writing too fast, disturb errors due to multiple write cycles to a single page, disturb errors due to imbalanced utilization of a particular erase block, and the like.

By writing incoming payload data in the order in which it was received, the time order of the incoming payload data is preserved. Further, such an approach can eliminate position dependence of payload data within an erase block. Stated another way, because incoming payload data is written in the order it was received, there may be no ordinal relationship among pages of payload data stored within an erase block. In particular, payload data stored within an erase block may be entirely disjoint, with each page of payload data having no relationship to any other page of payload data.

Further, certain modern flash memory devices (for example, Intel SD58 series NAND flash memory) impose the restriction that pages within an erase block must be written in sequential order. However, prior flash memory management systems comprising these flash memory devices did not write incoming data directly to the flash memory device in the order in which it was received. Rather, these prior systems may have held incoming data in a buffer until a full erase block of related data was received, and then wrote the entire erase block of related data to the flash memory device at once (i.e. these prior systems wrote sequences of contiguous data differently than sequences of random data). When operating within the constraints presented by such devices, and in accordance with an exemplary aspect of the present invention, a flash memory management system realizes improvements in data integrity by writing sequences of random data in the same manner as sequences of contiguous data. However, the principles of the present invention may be applied to all flash memory, and are not limited to flash memory which imposes the restriction that pages within an erase block must be written in sequential order. Additionally, the principles of the present invention may be applied to any storage technology which requires data to be erased on a blockwise basis.

With reference to FIG. 1, FIG. 2, FIG. 3A, FIG. 3B, and FIG. 4, in accordance with an exemplary embodiment, a flash memory management system 100 comprises a solid state drive 102. Solid state drive 102 may be coupled to a host computer 108. Solid state drive 102 comprises a flash chip array 110 and a flash chip controller 104. Flash chips 106 in flash chip array 110 are divided into erase blocks 312, and erase blocks 312 are divided into pages 314. One or more data structures, such as data tables 408, to support solid state drive 102 are constructed in RAM 402 of sequence and control machine 210.

Returning now to FIG. 1, in accordance with an exemplary embodiment, a solid state drive 102 is a storage medium capable of storing electronic information in a persistent form, typically in computer chips or other solid-state devices. In an exemplary embodiment, solid state drive 102 comprises a thumb drive. In other exemplary embodiments, solid state drive 102 comprises a storage medium in a desktop computer, a laptop computer, a smartphone, or a personal digital assistant. Solid state drive 102 can be used in place of magnetic disk drives or certain other magnetic, optical, or electronic storage components in computing systems. Solid state drive 102 can provide significant advantages when compared to magnetic or optical storage, such as faster seek times, faster access times, improved ruggedness and reliability, lower operating noise, and lower power consumption. Depending on the configuration and components of a particular solid state drive 102, it may be compatible with computer storage interface protocols, including but not limited to Serial Advanced Technology Attachment (SATA), Parallel Advanced Technology Attachment (PATA), Small Computer System Interface (SCSI), IEEE 1394 (Firewire), Serial Attached SCSI (SAS), and Universal Serial Bus (USB). Further, solid state drive 102 may be configured to conform with standard storage form factors, such as “5.25 inch”, “3.5 inch” (commonly used in desktop storage products), and “2.5 inch” (commonly used in mobile computing products).

A flash chip array, such as flash chip array 110, comprises one or more flash chips 106. Any number of flash chips may be selected. In one exemplary embodiment, a flash chip array 110 comprises sixteen flash chips. In various exemplary embodiments, other suitable numbers of flash chips 106 may be selected, such as one, two, four, eight, or thirty-two flash chips. Flash chips 106 may be selected to meet storage size, power draw, or other desired flash chip array characteristics.

In an exemplary embodiment, flash chip array 110 comprises flash chips 106 having similar storage sizes. In various other exemplary embodiments, flash chip array 110 comprises flash chips 106 having different storage sizes. Any number of flash chips 106 having various storage sizes may be selected. Further, a number of flash chips 106 having a significant number of unusable erase blocks 312 and/or pages 314 may comprise flash chip array 110. In this manner, one or more flash chips 106 which may have been unsuitable for use in a particular solid state drive 102 can now be utilized. For example, a particular flash chip 106 may contain 2 gigabytes of storage capacity. However, due to manufacturing processes or other factors, 1 gigabyte of the storage capacity on this particular flash chip 106 may be unreliable or otherwise unusable. Similarly, another flash chip 106 may contain 4 gigabytes of storage capacity, of which 512 megabytes are unusable. These two flash chips 106 may be included in a flash chip array 110. In this example, flash chip array 110 contains 6 gigabytes of storage capacity, of which 4.5 gigabytes are usable. Thus, the total storage capacity of flash chip array 110 may be reported as any size up to and including 4.5 gigabytes. In this manner, the cost of solid state drive 102 may be reduced, as flash chips 106 with higher defect densities are often less expensive. Moreover, because flash chip array 110 may utilize various types and sizes of flash memory, one or more flash chips 106 may be utilized instead of discarded as waste.

In an exemplary embodiment, the reported storage capacity of flash chip array 110 may be smaller than the actual storage capacity, for such reasons as to compensate for the development of bad blocks, provide space for defragmentation operations, provide space for index information, extend the useable lifetime of flash chip array 110, and the like. For example, flash chip array 110 may comprise flash chips 106 having a total useable storage capacity of 10 gigabytes. However, the reported capacity of flash chip array 110 may be 2 gigabytes. Thus, because no more than 2 gigabytes of space within flash chip array 110 will be utilized for active storage, individual memory elements in flash chip array 110 may be utilized in a reduced manner, and the useable lifetime of flash chip array 110 may be extended. In the present example, when the reported capacity of flash chip array 110 is 2 gigabytes, the useable lifetime of a flash chip array 110 with useable storage capacity of ten gigabytes would be about five times longer than the useable lifetime of a flash chip array 110 containing only 2 gigabytes of total useable storage capacity, because the reported storage capacity is the same but the actual capacity is five times larger.

In various embodiments, flash chip array 110 comprises multiple flash chips 106. As disclosed hereinbelow, each flash chip 106 may have one or more bad pages 314 which are not suitable for storing data. However, solid state drive 102 may be configured in a manner which allows all good pages 314 within each flash chip 106 to be utilized.

Flash chips 106 may be mounted on a printed circuit board. Flash chips 106 may also be mounted in other suitable configurations in order to facilitate their use in forming flash chip array 110.

In an exemplary embodiment, flash chip array 110 is configured to interface with flash controller 104. Flash controller 104 is configured to facilitate reading, writing, erasing, and other operations on flash chips 106. Flash controller 104 may be configured in any suitable manner to facilitate operations on flash chips 106 in flash chip array 110.

In flash chip array 110, and according to an exemplary embodiment, individual flash chips 106 are configured to receive a chip select (CS) signal. A CS signal is configured to locate, address, and/or activate a flash chip 106. For example, in a flash chip array 110 with eight flash chips 106, a three-bit binary CS signal would be sufficient to uniquely identify each individual flash chip 106. In an exemplary embodiment, CS signals are sent to flash chips 106 from flash controller 104. In another exemplary embodiment, discrete CS signals are decoded within flash controller 104 from a three-bit CS value and applied individually to each of the flash chips 106.

In an exemplary embodiment, multiple flash chips 106 in flash chip array 110 may be accessed simultaneously. Simultaneous access can facilitate performance gains, such as improvements in responsiveness and throughput of flash chip array 110. For example, flash chips 106 are typically accessed through an interface, such as an 8-bit bus interface. If two identical flash chips 106 are provided, these flash chips 106 may be logically connected such that an operation (read, write, erase, and the like) performed on the first flash chip 106 is also performed on the second flash chip 106, utilizing identical commands and addressing. Thus, data transfers happen in tandem, effectively doubling the effective data rate without increasing data transfer latency. However, in this configuration, the logical page size and/or logical erase block size may also double. Moreover, any number of similar and/or different flash chips 106 may comprise flash chip array 110, and flash controller 104 may utilize flash chips 106 within flash chip array 110 in any suitable manner in order to achieve one or more desired performance and/or configuration objectives (e.g., storage size, data throughput, data redundancy, flash chip lifetime, read time, write time, erase time, and the like).

A flash chip, such as flash chip 106, may be an integrated circuit fabricated on a single piece of silicon or other suitable substrate. Alternatively, flash chip 106 may comprise integrated circuits fabricated on multiple substrates. One or more flash chips 106 may be packaged together in a standard package such as a thin small outline package, ball grid array, stacked package, land grid array, quad flat package, or other suitable package, such as standard packages approved by the Joint Electron Device Engineering Council (JEDEC). A flash chip 106 may also conform to specifications promulgated by the Open NAND Flash Interface Working Group (OFNI). A flash chip 106 can be fabricated and packaged in any suitable manner for inclusion in a flash chip array 110.

Flash chip 106 may contain any number of non-volatile memory elements, such as NAND flash elements, NOR flash elements, and the like. Flash chip 106 may also contain control circuitry. Control circuitry can facilitate reading, writing, erasing, and other operations on non-volatile memory elements. Such control circuitry may comprise elements such as microprocessors, registers, buffers, counters, timers, error correction circuitry, and input/output circuitry. Such control circuitry may also be located external to flash chip 106.

In an exemplary embodiment, non-volatile memory elements on flash chip 106 are configured as a number of erase blocks 0 to N. With reference to FIG. 3A and FIG. 3B, a flash chip 106, such as flash chip 310, comprises one or more erase blocks 312. Each erase block 312 comprises one or more pages 314. Each page 314 comprises a subset of the non-volatile memory elements within an erase block 312. Each erase block 312 contains about 1/N of the non-volatile memory elements located on flash chip 310.

In general, because flash memory, particularly NAND flash memory, may often be erased only in certain discrete sizes at a time, flash chip 310 typically contains a large number of erase blocks 312. Such an approach allows operations on a particular erase block 312, such as erase operations, to be conducted without disturbing data located in other erase blocks 312. Alternatively, were flash chip 310 to contain only a small number of erase blocks 312, data to be erased and data to be preserved would be more likely to be located within the same erase block 312. In the extreme example where flash chip 310 contains only a single erase block 312, any erase operation on any data contained in flash chip 310 would require erasing the entire flash chip 310. If any data on flash chip 310 was desired to be preserved, that data would need to be read out before the erase operation, stored in a temporary location, and then re-written to flash chip 310. Such an approach has significant overhead, and could lead to premature failure of the flash memory due to excessive, unnecessary read/write cycles.

With continued reference to FIG. 3A and FIG. 3B, an erase block 312 comprises a subset of the non-volatile memory elements located on flash chip 310. Although memory elements within erase block 312 may be programmed and read in smaller groups, all memory elements within erase block 312 may only be erased together. Each erase block 312 is further subdivided into any suitable number of pages 314. A flash chip array 110 may be configured to comprise flash chips 310 containing any suitable number of pages 314.

A page 314 comprises a subset of the non-volatile memory elements located within an erase block 312. In an exemplary embodiment, there are 64 pages 314 per erase block 312. To form flash chip array 110, flash chips 106 comprising any suitable number of pages 314 per erase block 312 may be selected.

In addition to memory elements used to store payload data, a page 314 may have memory elements configured to store error detection information, error correction information, and/or other information intended to ensure safe and reliable storage of payload data. In an exemplary embodiment, metadata stored in a page 314 is protected by error correction codes. In various exemplary embodiments, a portion of erase block 312 is protected by error correction codes. This portion may be smaller than, equal to, or larger than one page.

In an exemplary embodiment, erase block 312 comprises 64 pages 314. Of these pages, 63 are configured to store payload data, such as data received from an external source, such as host computer 108. The final page is configured to contain erase block index information. Furthermore, any number of pages in erase block 312 may be used to store payload data and/or erase block index information. In an exemplary embodiment, erase block index information stored in the final page comprises a duplicate copy of metadata associated with each page 314 configured to store payload data. Additionally, index information for a particular erase block 312 may be stored in the final page of a different erase block 312. For example, index information for a particular erase block 312 located on a flash chip 106 may be stored in an erase block 312 located on a different flash chip 106. Erase block index information may be stored in any suitable location configured to store index information. Multiple copies of erase block index information for a particular erase block 312 may be stored at various locations in flash chip array 110.

Returning now to FIG. 4 and in an exemplary embodiment, index information is used to construct or reconstruct one or more data structures. For example, an erase block table, such as a physical erase block (PEB) table 406, and/or a page table, such as a logical to physical (L2P) table 404, can be created in RAM 402 in sequence and control machine 210. Index information for an erase block 312 may be constructed, stored, or otherwise held in RAM 402 in sequence and control machine 210. In accordance with an exemplary embodiment, index information for an erase block 312 is written to final page 314 when all other pages 314 within erase block 312 have been filled with payload data. Index information for an erase block 312 may also be written to final page 314 when a write operation to erase block 312 is completed, even though all other pages within erase block 314 may not yet be filled with payload data. Index information for an erase block 312 may be written to final page 314 at any time in order to provide an accurate record of the contents and status of erase block 312. Moreover, index information for a particular erase block 312 may also comprise an indication of which pages 314 within erase block 312 are damaged or otherwise unusable.

When an erase block 312 contains no valid payload data, it is ready to be erased. The index information for this erase block 312 may be marked as obsolete. An erase block 312 may be erased at any appropriate time.

Turning now to FIG. 2, a flash controller 104, such as flash controller 200, may comprise any suitable circuitry configured to interface with flash chips 106 and with host computer 108. For example, flash controller 200 may be implemented on a field programmable gate array (FPGA). In another example, flash controller 200 may be implemented on an application specific integrated circuit (ASIC). Further, flash controller 200 may be implemented on any suitable hardware. In accordance with an exemplary embodiment, flash controller 200 comprises a buffer-host machine 202, a media-buffer machine 204, a data buffer 206, a local buffer 208, and a sequence and control machine 210. Flash controller 200 is configured to communicate with host computer 108 and with flash chips 106.

Buffer-host machine 202 may comprise any suitable circuitry configured to provide an interface between data buffer 206 and an external data source, such as host computer 108. In an exemplary embodiment, buffer-host machine 202 is configured to interface with host computer 108. Buffer-host machine 202 is further configured to control the flow of payload data between host computer 108 and data buffer 206. Buffer-host machine 202 is configured to receive and optionally queue commands from host computer 108. Any errors resulting from these commands are returned to host computer 108 on behalf of sequence and control machine 210. In particular, commands that do not involve the transfer of payload data are not applied to sequence and control machine 210, but instead are handled directly by buffer-host machine 202.

In an exemplary embodiment, for a solid state drive 102 configured as an ATA drive replacement, such non-payload commands comprise ATA commands, such as the ATA IDENTIFY and ATA SET FEATURES commands. In an exemplary embodiment, buffer-host machine 202 is configured to have logical block address level visibility into data buffer 206. Such a configuration allows buffer-host machine 202 to reduce latency. Further, it allows buffer-host machine 202 to manage data transfers which are less than one page in size.

Data buffer 206 may comprise any suitable circuitry configured to connect media-buffer machine 204 and buffer-host machine 202. In an exemplary embodiment, data buffer 206 is a page-sized buffer. In other embodiments, data buffer 206 may be larger than one page. Data buffer 206 may be any size suitable to be configured to connect media-buffer machine 204 and buffer-host machine 202. In an exemplary embodiment, data buffer 206 is configured to hold data as a short-time cache (for example, for less-than-page sized operations). In various exemplary embodiments, data buffer 206 is configured as a first-in-first-out (FIFO) buffer. In other exemplary embodiments, data buffer 206 is configured in any suitable manner to connect media-buffer machine 204 and buffer-host machine 202. Further, data buffer 206 may be configured to transfer data between host-buffer machine 202 and media-buffer machine 204.

Media-buffer machine 204 may comprise any suitable circuitry configured to provide an interface between data buffer 206 and flash chip array 110. In an exemplary embodiment, media-buffer machine 204 is configured to communicate with and control one or more flash chips 106. In various exemplary embodiments, media-buffer machine 204 is configured to provide error correction code generation and checking capabilities.

Local buffer 208 is a buffer configured to capture local data. In an exemplary embodiment, local buffer 208 can capture error correction data.

Sequence and control machine 210 may comprise any suitable circuitry configured to receive payload data processing commands from buffer-host machine 202, and configured to implement the logic and computational processes necessary to carry out and respond to these commands. In an exemplary embodiment, sequence and control machine 210 is configured to create, access, and otherwise manage data structures, such as data tables 408. Further, sequence and control machine 210 is configured to coordinate buffer-host machine 202, data buffer 206, local buffer 208, and media-buffer machine 204 in order to implement tasks, for example read, write, garbage collection, and/or the like.

Turning again to FIG. 4, in accordance with an exemplary embodiment, one or more data structures, such as data tables 408, are maintained in random access memory (RAM) of sequence and control machine 210, such as RAM 402. Data tables 408 are configured to facilitate read, write, erase, and other operations on flash chip array 110 in solid state drive 102.

According to an exemplary embodiment, data tables 408 are stored in their entirety in RAM 402 of sequence and control machine 210. In this exemplary embodiment, no portion of data tables 408 is stored on a hard disk drive, solid state drive, magnetic tape, or other non-volatile medium. Prior approaches were unable to store data tables 408 in their entirety in RAM 402 due to the limited availability of space in RAM 402. But now, large amounts of RAM 402, such as 1 gigabyte, 4 gigabytes, or more, are relatively inexpensive and are now commonly available for use in sequence and control machine 210. Because data tables 408 are stored in their entirety in RAM 402, which may be quickly accessed, system speed can be increased when compared to former approaches which stored only a small portion of a data table in RAM 402, and stored the remainder of a data table on a slower, nonvolatile medium. In other exemplary embodiments, portions of data tables 408, such as infrequently accessed portions, are strategically stored in non-volatile memory. Such an approach balances the performance improvements realized by keeping data tables 408 in RAM 402 with the potential need to free up portions of RAM 402 for other uses.

With continued reference to FIG. 4, in an exemplary embodiment, a logical page is mapped to a particular area of physical non-volatile memory on a flash chip 106 by use of a table, such as a logical to physical (L2P) table 404. Entries in L2P table 404 contain physical addresses for logical memory pages. Entries in L2P table 404 may also contain additional information about the page in question. The size of L2P table 404 defines the apparent capacity of solid state drive 102.

L2P table 404 contains information configured to map a logical page to a logical erase block and page. For example, in an exemplary embodiment, in L2P table 404 an entry contains 22 bits: an erase block number (16 bits), and a page offset number (6 bits). With reference to FIG. 3A and FIG. 3B, the erase block number identifies a specific logical erase block 312 in solid state drive 102, and the page offset number identifies a specific page 314 within erase block 312. The number of bits used for the erase block number, and the page offset number may be increased or decreased depending on the number of flash chips 106, erase blocks 312, and/or pages 314 desired to be indexed.

With continued reference to FIG. 3A, FIG. 3B, and FIG. 4, erase blocks 312 in a solid state drive 102 may be managed via a table, such as a physical erase block (PEB) table 406. PEB table 406 may be configured to contain any suitable information about erase blocks 312. In an exemplary embodiment, PEB table 406 contains information configured to locate erase blocks 312 in flash chip array 110.

In an exemplary embodiment, PEB table 406 is located in its entirety in RAM 402 of sequence and control machine 210. Further, PEB table 406 is configured to store information about each erase block 312 in flash chip array 110, such as the flash chip 106 where erase block 312 is located (i.e. a chip select (CS) value), the location of erase block 312 on flash chip 106, the state (e.g. dirty, erased, and the like) of pages 314 in erase block 312, the number of pages 314 in erase block 312 which currently hold payload data, the next page 314 within erase block 312 available for writing incoming payload data, information regarding the wear status of erase block 312, and the like. Further, pages 314 within erase block 312 may be tracked, such that when a particular page is deemed unusable, the remaining pages in erase block 312 may still be used, rather than marking the entire erase block 312 containing the unusable page as unusable.

Additionally, the size and/or contents of PEB table 406 and/or other data structures 408 may be varied in order to allow tracking and management of operations on portions of erase block 312 smaller than one page in size. Prior approaches typically tracked a logical page size which was equal to the physical page size of the flash memory device in question. In contrast, because an increase in a physical page size often imposes additional data transfer latency or other undesirable effects, in various exemplary embodiments, a logical page size smaller than a physical page size is utilized. In this manner, data transfer latency associated with solid state drive 102 may be reduced. For example, when a logical page size LPS is equal to a physical page size PPS, the number of entries in PEB table 406 may be a value X. By doubling the number of entries in PEB table 406 to 2X, twice as many logical pages may be managed. Thus, logical page size LPS may now be half as large as physical page size PPS. Stated another way, two logical pages may now correspond to one physical page. Similarly, in an exemplary embodiment, the number of entries in PEB table 406 is varied such that any desired number of logical pages may correspond to one physical page.

Moreover, the size of a physical page in a first flash chip 106 may be different than the size of a physical page in a second flash chip 106. Thus, in various exemplary embodiments, PEB table 406 may be configured to manage a first number of logical pages per physical page for first flash chip 106, a second number of logical pages per physical page for second flash chip 106, and so on. In this manner, multiple flash chips 106 of various capacities and/or configurations may be utilized within solid state drive 102.

Additionally, a flash chip 106 may comprise one or more erase blocks 312 containing at least one page that is “bad”, i.e. defective or otherwise unreliable and/or inoperative. In previous approaches, when a bad page was discovered, the entire erase block 312 containing a bad page was marked as unusable, preventing other “good” pages within that erase block 312 from being utilized. To avoid this condition, in various exemplary embodiments, PEB table 406 and/or other data tables 408, such as a defect list, may be configured to allow use of good pages within an erase block 312 having one or more bad pages. For example, PEB table 406 may comprise a series of “good/bad” indicators for one or more pages. Such indicators may comprise a status bit for each page. If information in PEB table 406 indicates a particular page is good, that page may be written, read, and/or erased as normal. Alternatively, if information in PEB table 406 indicates a particular page is bad, that page may be blocked from use. Stated another way, sequence and control machine 210 may be prevented from writing to and/or reading from a bad page. In this manner, good pages within flash chip 106 may be more effectively utilized, extending the lifetime of flash chip 106.

In addition to L2P table 404 and PEB table 406, other data structures, such as data tables 408, may be configured to manage the contents of flash chip array 110. In an exemplary embodiment, L2P table 404, PEB table 406, and all other data tables 408 are located in their entirety in RAM 402 of sequence and control machine 210. In other exemplary embodiments, L2P table 404, PEB table 406, and all other data tables 408 are located in any suitable location configured for storing data structures.

In an exemplary embodiment, data structures, such as data tables 408, are constructed using erase block index information stored in the final page of each erase block 312. Data tables 408 are constructed when solid state drive 102 is powered on. In another exemplary embodiment, data tables 408 are constructed using the metadata associated with each page 314 in flash chip array 110. Again, data tables 408 are constructed when solid state drive 102 is powered on. Data tables 408 may be constructed, updated, modified, and/or revised at any appropriate time to enable operation of solid state drive 102.

With reference now to FIGS. 1 and 5A, and in accordance with an exemplary embodiment, metadata, error correcting information, and/or the like, may be stored separately from payload data. For example, a separately addressable flash chip 106 (for example, flash chip 530), or one or more non-flash memory elements may be utilized in combination with one or more flash chips 106 to achieve improved performance by storing metadata exclusively on flash chip 530. Flash chip 530 may be configured to store metadata, error correcting codes, and the like, for information contained within a flash chip array 110 (for example, flash chip array 510). Often, NAND flash memory devices, such as those from Intel, Samsung, and the like, are designed to be acceptable for use in a wide variety of applications at a low cost. Thus, these flash memory devices are configured based on design guidelines and/or assumptions or best guesses as to market requirements. Thus, these flash memory devices are often sized to accommodate four or eight disk blocks of 512 bytes each, plus a number of additional bytes for error correction codes, other metadata, and other implementation-specific data elements. The number of additional bytes provided may vary (for example, many Samsung devices provide 128 additional bytes per 4 kB stored, many Intel devices provide 218 additional bytes per 4 kB, stored, and so on). While these additional bytes may be sufficient to store desired error correction codes for up to eight logical blocks as defined by the InterNational Committee for Information Technology Standards (INCITS) committee T13 (ATA standards group) and committee T10 (SCSI standard group), storage of information beyond basic error correction codes and basic metadata may be desired, and this information may not fit in the limited space provided. Moreover, if the logical block address size is varied, additional storage space may be needed. Therefore, because the number of vendors providing flash memory with extended additional storage bytes may be limited, other solutions for storing error correcting codes, metadata, and/or the like are desirable. Accordingly, this information may be stored in flash chip 530, eliminating the need to store this information in the limited space available within flash chip array 510, and freeing up additional portions of flash chip array 510 for storage of payload data.

Further, metadata associated with a flash chip array 510 may be stored in any suitable location outside flash chip array 510. With reference now to FIGS. 1 and 5B, and in accordance with an exemplary embodiment, metadata, error correcting information, and the like, may be stored separately from payload data. In this manner, metadata may be retrieved without need to access a flash chip. Moreover, by storing the metadata in a high-performance memory, faster access and/or random access to the metadata may be enabled. Additionally, space within flash chip array 110 previously used to store metadata may now be utilized to store payload data, increasing the effective storage capacity of flash chip array 110. Further, solid state drive 102 may be made more reliable by storing multiple copies of metadata, error correcting information, and the like.

In an exemplary embodiment, a solid state drive 102 (for example, solid state drive 502) comprises a controller 104 (for example, controller 504) coupled to a flash chip array 110 (for example, flash chip array 510) comprised of one or more flash chips 106 (for example, flash chips 506). Solid state drive 102 further comprises a non-volatile metadata storage memory 520 coupled to controller 504. Metadata storage memory 520 may comprise any suitable non-volatile storage technology. Moreover, to increase reliability, multiple metadata storage memories 520 may be coupled to controller 504, and each metadata storage memory 520 may contain similar and/or the same information. In this manner, information contained in a particular metadata storage memory 520 can be preserved even if another metadata storage memory 520 is damaged, fails, or otherwise becomes unreadable. Further, a particular metadata storage memory 520 may comprise any number of individual memory elements, integrated circuits, chips, and/or the like, as desired.

In an exemplary embodiment, metadata storage memory 520 is configured to store metadata, error correcting codes, and/or other desired information about information stored in flash chip array 510. Due to the comparatively small storage size of the error correcting codes and/or metadata associated with flash chip array 510 when compared with the total storage capacity of flash chip array 510, alternative memory technologies other than flash memory may be desirably employed for metadata storage memory 520. For example, magnetic RAM (MRAM), ferromagnetic RAM (FRAM), phase-change memory (PC-RAM), or other suitable RAM, may be utilized. Moreover, these technologies may provide true random read and/or write operations, and may be capable of writing single bits to either state without an erase requirement. Thus, individual portions of the information stored in metadata storage memory 520 may be more easily accessed and/or manipulated when compared with information stored in a memory configured for block-based read and/or write operations. For example, use of random access memory in metadata storage memory 520 allows solid state drive 502 to avoid the overhead associated with defragmentation operations within metadata storage memory 520.

In an exemplary embodiment, metadata storage memory 520 provides 256 bytes of storage for error correcting codes and/or metadata per 4 kB of storage in flash chip array 510. Thus, if the storage capacity of flash chip array 510 is 256 GB, the storage capacity of metadata storage memory 520 may be 16 GB. Moreover, information stored in metadata storage memory 520 may be accessed in random fashion and/or without need to simultaneously access flash chip array 510. Further, information stored in metadata storage memory 520 may be accessed, updated, deleted, and/or the like at any suitable time, for example: before, during, or after writing to flash chip array 510; before, during, or after deleting information from flash chip array 510; before, during, or after moving information within flash chip array 510; and/or the like. In this manner, performance of solid state drive 502 may be improved, as error correcting information, metadata, and the like, for information stored in flash chip array 510, may be written and/or retrieved at a higher rate of speed as compared to operations within flash chip array 510. Moreover, for additional reliability, metadata, error correction codes, and the like, may also be stored in any desired location within flash chip array 510, in addition to being stored in metadata storage memory 520.

Principles of the present disclosure may suitably be combined with principles of utilizing a logical page size different from a physical page size as disclosed in co-pending U.S. patent application Ser. No. 12/424,461 filed on Apr. 15, 2009, now U.S. Patent Application Publication No. 2009/0259805 entitled “FLASH MANAGEMENT USING LOGICAL PAGE SIZE”, the contents of which are hereby incorporated by reference in their entirety.

Principles of the present disclosure may suitably be combined with principles of bad page tracking as disclosed in co-pending U.S. patent application Ser. No. 12/424,464 filed on Apr. 15, 2009, now U.S. Patent Application Publication No. 2009/0259806 entitled “FLASH MANAGEMENT USING BAD PAGE TRACKING AND HIGH DEFECT FLASH MEMORY”, the contents of which are hereby incorporated by reference in their entirety.

Moreover, principles of the present disclosure may suitably be combined with any number of principles disclosed in any one of and/or all of the co-pending U.S. Patent Applications incorporated by reference herein. Thus, for example, a combination of memory management techniques can include use of a logical page size different from a physical page size, use of separate metadata storage, use of bad page tracking, use of sequential write techniques and/or use of circular leveling techniques.

As will be appreciated by one of ordinary skill in the art, principles of the present disclosure may be reflected in a computer program product on a tangible computer-readable storage medium having computer-readable program code means embodied in the storage medium. Any suitable computer-readable storage medium may be utilized, including magnetic storage devices (hard disks, floppy disks, and the like), optical storage devices (CD-ROMs, DVDs, Blu-Ray discs, and the like), flash memory, and/or the like. These computer program instructions may be loaded onto a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions that execute on the computer or other programmable data processing apparatus create means for implementing the functions specified in the flowchart block or blocks. These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks.

While the principles of this disclosure have been shown in various embodiments, many modifications of structure, arrangements, proportions, the elements, materials and components, used in practice, which are particularly adapted for a specific environment and operating requirements may be used without departing from the principles and scope of this disclosure. These and other changes or modifications are intended to be included within the scope of the present disclosure and may be expressed in the following claims.

In the foregoing specification, the invention has been described with reference to various embodiments. However, one of ordinary skill in the art appreciates that various modifications and changes can be made without departing from the scope of the present invention as set forth in the claims below. Accordingly, the specification is to be regarded in an illustrative rather than a restrictive sense, and all such modifications are intended to be included within the scope of the present invention. Likewise, benefits, other advantages, and solutions to problems have been described above with regard to various embodiments. However, benefits, advantages, solutions to problems, and any element(s) that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as a critical, required, or essential feature or element of any or all the claims. As used herein, the terms “comprises,” “comprising,” or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Also, as used herein, the terms “coupled,” “coupling,” or any other variation thereof, are intended to cover a physical connection, an electrical connection, a magnetic connection, an optical connection, a communicative connection, a functional connection, and/or any other connection. When “at least one of A, B, or C” is used in the claims, the phrase is intended to mean any of the following: (1) at least one of A; (2) at least one of B; (3) at least one of C; (4) at least one of A and at least one of B; (5) at least one of B and at least one of C; (6) at least one of A and at least one of C; or (7) at least one of A, at least one of B, and at least one of C. 

1. A method for flash memory management, comprising: storing, in a flash memory, at least one of metadata or error correcting information associated with payload data stored in one or more logical pages in the flash memory; storing, in a metadata storage memory, the at least one of metadata or error correcting information associated with payload data stored in one or more logical pages in the flash memory; constructing, in the metadata storage memory, a data table associated with the flash memory, wherein entries of the data table correspond to logical pages within the flash memory, and wherein entries of the data table comprise the at least one of metadata or error correcting information associated with payload data stored in the logical pages; and providing a logical to physical (L2P) table and a physical erase block (PEB) table configured to locate payload data written to the flash memory, wherein the L2P table and the PEB table are contained entirely in random access memory.
 2. The method of claim 1, wherein the metadata storage memory is configured for random access.
 3. The method of claim 1, wherein the flash memory comprises a plurality of erase blocks for storing payload data, wherein each erase block for storing payload data in the flash memory comprises an index page for storing at least one of metadata or error correcting information for the logical pages in the erase block, wherein the data table is constructed from the index page of each erase block for storing payload data in the flash memory, and wherein the data table is constructed responsive to the flash memory being powered on.
 4. The method of claim 1 wherein entries of the data table and the PEB table correspond to logical pages within the flash memory, and wherein the size of the logical pages is smaller than the size of a physical page in the flash memory.
 5. The method of claim 4, further comprising varying the size of the PEB table in order to vary the size of a logical page with respect to a physical page in the flash memory.
 6. The method of claim 1, further comprising updating the data table responsive to payload data being stored in at least one logical page within the flash memory, wherein the payload data is written to the flash memory in the order it was received from a host, and wherein writing the payload data in the order it was received from the host comprises: locating a target page in an erase block in the flash memory; combining the payload data with metadata; writing the payload data and the metadata to the target page; updating the logical to physical (L2P) table; updating the physical erase block (PEB) table; and responsive to page offset information indicating all pages in the erase block except an index page are full, writing index information for the erase block to the index page in the erase block.
 7. The method of claim 6, wherein writing the payload data in the order it was received from the host further comprises writing the payload data in a sequential manner within at least one erase block in the flash memory.
 8. The method of claim 1, further comprising retrieving at least one of metadata or error correcting information without accessing the flash memory.
 9. The method of claim 1, further comprising storing payload data in the flash memory, wherein the payload data is stored in memory elements in the flash memory intended to store at least one of metadata or error correcting information.
 10. The method of claim 1, wherein storing at least one of metadata or error correcting information comprises storing, in an erase block in the flash memory containing payload data, at least one of metadata or error correcting information associated with payload data stored in a different erase block in the flash memory.
 11. The method of claim 1, wherein the flash memory comprises a first flash memory chip for storing payload data and a second flash memory chip for storing payload data, wherein the payload data storage capacity of the first flash memory chip differs from the payload data storage capacity of the second flash memory chip.
 12. The method of claim 1, further comprising storing the data table on a flash chip in a solid state drive, wherein the flash chip is separately addressable from any portion of the flash memory used to store payload data.
 13. The method of claim 1, further comprising storing the data table in its entirety in a first location, and storing a copy of the data table in its entirety in a second location.
 14. The method of claim 13, wherein the first location is a first metadata storage memory within a solid state drive, and wherein the second location is a second metadata storage memory within the solid state drive.
 15. The method of claim 14, wherein the first metadata storage memory and the second metadata storage memory are located on different integrated circuits.
 16. The method of claim 1, wherein the PEB table tracks pages within erase blocks of the flash memory such that when a particular page is deemed unusable for storing payload data, other pages within the same erase block of the flash memory may still be used for storing payload data.
 17. The method of claim 1, further comprising: receiving payload data from a host; and writing the payload data to the flash memory in a location identified by the flash memory manufacturer for storage of at least one of metadata or error correcting information.
 18. The method of claim 1, wherein the flash memory comprises a first erase block containing payload data and a second erase block containing payload data, and wherein the first erase block comprises an index page for storing erase block index information for payload data written to pages in the second erase block.
 19. A data storage system, comprising: a first memory configured for block-based erase operations; a controller in communication with the first memory, wherein the first memory stores at least one of metadata or error correcting information associated with payload data stored in one or more logical pages in the first memory; and a second memory configured for random access in communication with the controller, wherein the second memory: stores at least one of metadata or error correcting information associated with payload data stored in one or more logical pages in the first memory, includes a data table, wherein entries of the data table correspond to logical pages within first memory and comprise at least one of metadata or error correcting information associated with the logical pages, and includes a logical to physical (L2P) table and a physical erase block (PEB) table configured to locate payload data written to the first memory and contained entirely in random access memory.
 20. The data storage system of claim 19, wherein the controller comprises a buffer-host machine, a media-buffer machine, a data buffer, a local buffer, and a sequence and control machine.
 21. The data storage system of claim 19, wherein the controller is configured to write incoming payload data to an erase block in the first memory in the order it was received from a host.
 22. The data storage system of claim 19, further comprising updating the data table responsive to payload data being stored in at least one logical page within the first memory, wherein the payload data is written to the first memory in the order it was received from a host.
 23. A tangible computer-readable storage medium having stored thereon instructions to perform operations comprising: storing, in a flash memory, at least one of metadata or error correcting information associated with payload data stored in one or more logical pages in the flash memory; storing, in a metadata storage memory, the at least one of metadata or error correcting information, associated with payload data stored in one or more logical pages in the flash memory; and constructing, in the metadata storage memory, a data table associated with the flash memory, wherein entries of the data table correspond to logical pages within the flash memory, and wherein entries of the data table comprise at least one of metadata or error correcting information associated with payload data stored in the logical pages; and providing a logical to physical (L2P) table and a physical erase block (PEB) table configured to locate payload data written to the flash memory, wherein the L2P table and the PEB table are contained entirely in random access memory. 